Skip to main content

Flow Trigger FAQs

Frequently asked questions for the Flow Trigger guide.

How Do I Use Parent Process Id?​

The Parent ProcessId field allows linking a newly triggered process to the current process. This creates a hierarchical structure in flow history, showing which processes were initiated by others.

When Should I Use Parent ProcessId?​

You should use it if:

  • You want to maintain traceability between the initiating and triggered flows.
  • You want the child flow to appear under the parent in the flow history view.

What Can I Enter in This Field?​

You can use:

  • ({{ProcessId}}): This is the default option and refers to the ID of the current (parent) process.
  • ({{SomeVariable.Value}}): You can pass the process ID dynamically from a variable.
  • A static string if you have a custom tracking system.

What Happens If I Leave It Blank?​

If the Parent ProcessId is empty:

  • The triggered process will not be linked to the current one.
  • It will appear independently in the flow history.

Tip​

Always use ({{ProcessId}}) unless you have a specific reason not to. This ensures flow linkage is preserved across processes.

General Behavior​

General Behavior of Flow Trigger​

The Flow Trigger object allows designers to start a different flow from the same or another project without writing code. This is especially useful when a workflow must initiate another process under certain conditions.

Single Process Trigger​

  • When you want to trigger only one process, you can configure the parameters directly in the Parameters section of the object.

Multiple Processes Trigger​

  • When triggering multiple processes, a DataGrid control must be placed on the form.
  • This grid should contain rows representing the different sets of parameters to be used for triggering each process.
  • The Flow Trigger object references this DataGrid to perform the multi-trigger operation.

Appearance Panel Overview​

  • Object Name: Internal name used to reference the object in code.
  • Caption: The visible title of the object on the design screen.
  • Is Lock: Locks the position of the object during design.
  • Size: Controls the width and height.

Properties Overview​

  • Source: Refers to the Document and Control (DataGrid) that hold the parameter data.
  • Trigger: Defines which project and flow should be triggered and who starts it.
  • Parameters: Defines which variable values will be passed to the triggered flow(s).

Common Usage Scenarios​

  • Starting a leave request approval process when a form is submitted.
  • Triggering a separate document review process from within another workflow.
  • Sending information to multiple workflows based on a grid of approval lines.

Additional Info​

  • If a configuration is incorrect, the system shows a red exclamation mark on the object.
  • Hovering the cursor over it displays a tooltip with the configuration e